example output:

# puppet plan run pe_status_check::infra_role_summary
Starting plan job ...
New Plan Job ID: 7

|
{
    "primary": [
        "primary.bastelfreak.local"
    ],
    "replica": [],
    "compiler": [
        "compiler.bastelfreak.local"
    ],
    "postgres": [],
    "legacy_primary": [],
    "legacy_compiler": []
}

@MartyEwings can I get your opinion on this? I would also like to add a switch so we return the hash by default, but could switch to a nice table. That will add https://github.com/voxpupuli/puppet-format as a dependency. PEADM does the same in https://github.com/puppetlabs/puppetlabs-peadm/blob/main/plans/status.pp

@MartyEwings can I get your opinion on this? I would also like to add a switch so we return the hash by default, but could switch to a nice table. That will add https://github.com/voxpupuli/puppet-format as a dependency. PEADM does the same in https://github.com/puppetlabs/puppetlabs-peadm/blob/main/plans/status.pp

@bastelfreak its always good to have a second way of getting the data, crucially this will tell you want it should be, rather than what is, (assuming no one tinkered with the fact), what are you thinking the use case of this data is.

With regards adding dependencies for formatting, as this is shipped with PE i cant add 3rd party deps

I'm working on a plan that writes a bolt config to use peadm::convert. I also could have queried the puppetdb for the pe_status_check_role fact, but that would have been the same effort and I think querying for classes is more secure.

Why cant we depend on other modules? PE alreadys ships a lot of modules.

Why cant we depend on other modules? PE alreadys ships a lot of modules.

PE only ships Modules that are authored internally, and even then, i have to get a lot of agreement from product to add anything new. I cant see a formatting module by VOX being approved for packaging and shipping

meh :(
But I can reuse the data in a wrapper plan and format it, that's okay to work with.

@bastelfreak ok, ill do a bit to due diligence on this, but i cant see a reason not to put it in, can you add a touch more about the source of the data in the docs, just so its clear "it gets x via y mechanism"

I added some notes and example output to the README.md.

I rebased this after #224 got merged.